home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
prog
/
super30a.zip
/
README.SM
< prev
next >
Wrap
Text File
|
1992-04-15
|
16KB
|
334 lines
*********************[ Programmer's SUPER-MAINT ]***************************
***************************[ version 3.00 ]*********************************
Thank you for using Programmer's SUPER-MAINT. It has many features, and
after you become comfortable using it you'll find it saves you much time
and effort in building your progamming projects.
This File is for the Shareware Trial Copy Version of SUPER-MAINT.
Use ORDER.FRM to Buy Your Registered Version.
****************************************************************************
**************[ A NOTE ABOUT OUR BULLETIN BOARD SYSTEM ]********************
As of February 1991 our Bulletin Board System (BBS) has been on line.
You may order any EmmaSoft product using the BBS, and registered users may
get technical support there. In addition there is a growing collection of
shareware programs, most notably those written by Association of Shareware
Professionals authors. There is no charge for accessing this board, and
downloads are unlimited (except by the daily time limit). The EmmaSoft
BBS is an approved ASP BBS.
607-533-7072 2400,1200,300bps N,8,1 24 hours No access Fee
****************************************************************************
******************[ The topics covered in this file are: ]******************
Disk Contents and Thanks
1. Installation*
2. New Since The Manual Was Printed
3. Upgrading from Earlier Versions
4. Compiler Support and Hardware Information*
5. The future
6. The sample program
*IMPORTANT NOTES: You must read these sections to get started...
**********************[ DISK CONTENTS AND THANKS: ]**************************
If you got SUPER-MAINT on 5 1/4" disks you MUST have DISK#1 AND DISK#2.
Both are contained on the 3 1/2" disk version.
The following files MUST be included in your SUPER-MAINT package. If
any of these are missing PLEASE CONTACT EMMASOFT IMMEDIATELY.
DISK #1 (or SUPER30A.ZIP)
DISK ZIP
-------- ---------
DISKID Validation File Required by Setup
ASP.TXT Shareware and ASP Information
ORDER.FRM Ordering Information and Form
README.SM This File
SETUP.EXE Automatic Setup Program
SETUP.HLP Help File For Setup Program
SMAK.EXE or SMAK.ZIP SUPER-MAINT Files
SMUPDATE.TXT A history of updates to SUPER-MAINT
SMUTIL.EXE or SMUTIL.ZIP Help files, Sample Program, Manual
VENDOR.DOC Shareware Distribution Info for Vendors
and Sysops
DISK #2 (OR SUPER30B.ZIP
(Setup lets you choose the appropriate configuration file and extracts
it for you. You can extract the configurations manually by running the
appropriate self-extracting file below.)
CONFIGS.EXE or CONFIGS.ZIP Language definitions and script templates
for Borland C, Clipper, Mix, Manx, Microsoft
C6 and earlier, Microsoft C7, SDK, Turbo C2,
Turbo C++, Watcom C, Zortech C, and the
EmmaSoft demo bogus compilers.
MANUAL.SM Operating Instructions
*****************[ Special thanks to the beta testers: ]*********************
Don Bowen (version 2) Tom Bruce
Ross M. Greenberg Todd Hutchinson (version 1)
Eric Landes Ralph Mace (version 2)
Allen Morris (version 2) Terry McConnel
Mike Ratledge Chip Rabinowitz
Peter Schulz (version 2) Dave Seidel
Vernon Six Mike Slater
Larry Weaver Adam Walker
Thanks for making SUPER-MAINT a better, more reliable program.
Special thanks to Chip Rabinowitz and Tom Bruce for major contributions,
solutions, solace, and advice.
*************************[ 1. INSTALLATION: ]*******************************
You should use SETUP.EXE to install SUPER-MAINT. (You'll need approximately
351KB of free disk space to complete an installation.) You must have DOS
version 3.0 or higher to insure SUPER-MAINT will work properly.
THE INSTALLATION PROGRAM WILL NOT TOUCH YOUR CONFIG.SYS FILE OR ANY
OTHER FILES ON YOUR COMPUTER. IF YOU CHOOSE TO LET SETUP UPDATE YOUR
AUTOEXEC.BAT FILE IT WILL DO SO.
On color systems type: SETUP <Enter>
On monochrome systems type: SETUP -m <Enter>
****************************************************************************
The first time you use SUPER-MAINT go into the setup menu to check your
settings and type in your libraries.
****************************************************************************
SETUP.EXE does NOT copy itself, the compressed (self-extracting files),
or text files to your hard drive. Only files that are needed to run
SUPER-MAINT are copied.
***************[ 2. New Since The Manual Was Printed: ]*********************
Chapter 5 (Chapter 3 in LITE manual):
-------------------------------------
TNAMES and Libraries as Dependents
When a library is included as a dependent on the TNAMES line it is also
added to the linker response file list of libraries to be linked. If all
libraries are added this way (no !L libraries) you must use a blank !L
statement for each memory model you use.
Chapter 7 (Chapter 5 in Lite Manual)
------------------------------------
*T can be used in the Linker, Librarian, and/or Compiler command groups
*CE is used (like *NE and *LE) to set a specific compiler response file
extension.
*RC can be used inside command groups. If that group is being used the
symbol defined there overrides the default symbol (usually @).
Appendix A:
-----------
Questions and Answers (Continued)
Q: I'm still not clear on when to use the *LCMND IS ___ statement in my
make files?
A: You can take two approaches to a library make file. A lot of people
write them the same way as program make files: using the object file
as the target for the code file that it is made of. There's nothing
wrong with this approach, but it means the object file must be present
to operate on a library. This may not be so safe if you are building
more than one memory model of the same library.
The other approach uses the library itself for all the targets. The
beauty of this approach is that if the library exists and the code has
not been updated, nothing has to happen regardless of the existence of
object files. You can use -ea to erase the objs for each model you
build (this isn't necessary if you are using -m*). If the code HAS
been updated, only that module has to be compiled and put into the
existing library.
When using the latter approach (you thought I'd never answer your
question!) SM needs a way of knowing which action block contains
the actual call to the librarian. It can't use the target, because
ALL the targets are the library. So you use the *LCMND IS ___
statement to let it know what the call to your librarian is: when
it sees that in an action block SM knows to write the response file
and build the library.
****************[ 3. UPGRADING FROM EARLIER VERSIONS: ]*********************
----RESPONSE FILE COMPATIBILITY-------
Version 3 of SUPER-MAINT generates response files on the fly. You must
have additional information in your make file for this to work. There are
two ways to deal with this for program building.
1. Add the new information to your make files. This should be easy using
SME. "Edit Old File," check your macros, name the files and
SUPER-MAINT===>.
2. If you want to use your old make and response files as-is you will have
to call SM with the -lr- flag. Before doing this you will need to
rename your response files. this is easy with the chgres utility
provided.
Earlier versions linker response file extensions: .LRS .LRM .LRL
Version 3 linker response file extensions: .LR1 .LR2 .LR3
To automatically change the extensions on your old response files go to
each directory you want to convert file names in and type:
CHGRES <Enter>
-----Your Setup------
Do not try to use SUPER.INI files from old versions of SUPER-MAINT. You
will have to re-enter your library lists into the new version.
-----Language Definitions------
You will also have to change your language definitions files. Use a text
editor to do the following to each one: Down arrow 7 times. At the first
character on the line press Enter. Down arrow 1 more time and press enter
twice. Now save the file.
Since SUPER.INI is different for version 3 you will have to re-enter your
libraries into the new version. Do not try to use your old SUPER.INI file.
**************************[ 4. COMPILER SUPPORT ]**************************
************************[ and Hardware Information ]************************
Version 3.00 and higher supports nearly any brand of Compiler thats linker
and librarian uses a response file. Compiler configuration is contained
in a script file called TEMPLATE.SM. Examples have been included for many
popular compilers. If yours is not included you can make a script manually
(see Chapter 6 in the manual, and the template worksheet).
BRAND SPECIFIC NOTES:
Borland, Clipper and MIX users will want to include the full path when
setting library names in SME.
SPECIAL NOTE FOR USERS OF MIX POWER C:
When using the MIX librarian (MERGE.EXE) the name of the library must not
be the same as the name of one of the modules in it. This is because
object modules and libraries both use the same (.MIX) extension.
**************************************************************************
* Please send us your configuration files if you have a compiler that is *
* not included in the list of pre-written configurations. *
**************************************************************************
Users of SUPER-MAINT on Novell LANs have reported under some conditions
the LAN time-stamps files with the server date and time regardless of that
set on the work station. Make utilities require that actual time/date
stamps be used. If -er, -t or other flags are not working, check the time/
date stamps the LAN is assigning to your files.
Notes for Aztec MANX C Support:
The TEMPLATE.SM script has been set to make SME automatically add the -f
command for calling response files. Do not manually enter the command in
a macro without changing the script or it will appear twice.
Paths:
Don't forget to set your *INCLUDE and *LIBRARY paths in TEMPLATE.SM before
you use SUPER-MAINT for the first time.
Libraries:
When setting up your libraries in the Setup menu you must type in the
complete path, and include the file extension. Example:
C:\LIBS\LMYLIB.LIB
TEMPLATE.SM has two additional *AB commands to work with the ORD program.
This places two additional action blocks in the make file before the
action block that calls the librarian program. The first changes the
name of the xxxxxxxx.LR0 file, and the second passes it through ORD,
renaming it to its original name. Because the file needs to be there
before the librarian needs it you should NOT use on-the-fly generation
of library response files. This means you will have to take out any
@xxxxxxxx.LNK statements and replace the extension with "AZT" (or if you
want another extension change the *AB commands in the template).
Many thanks to Allen Morris for providing information about Aztec Manx C.
SDK (Software Development Kit for Microsoft Windows
TEMPLATE.SM has an *AB and an *AA command to call the resource compiler
before and after linking.
BOGUS COMPILERS (DEMO Setup):
The "Demo" files were written for demonstrating Programmer's SUPER-MAINT at
COMDEX. The idea was to demonstrate the program without the overhead of
a real compiler, assembler, etc. The demonstration uses 5 programs: a
bogus compiler, bogus assembler, bogus linker, bogus librarian, and a
bogus debugger. These and the requisite language definition files
are placed on your disk when you choose "Demo" in SETUP.
The first two create bogus object files. These are actually ascii files
with the .OBJ extension. The linker does the same, but creates a file
with the .EXE extension. The librarian uses the .LIB extension. All
take similar arguments to their Microsoft counterparts, but the arguments
have no effect. The one exception is the /CO argument for the linker.
If you use /CO the ascii file starts with a line "Debugging Information
Included." The Bogus Debugger reads the first letter of the bogus .EXE
file. If it is a "D" the debugger starts normally. If not it displays
a message that debugging information is not included.
If you want to try Programmer's SUPER-MAINT without using real compilers,
etc. install the "Demo" files when SETUP.EXE asks "Who manufactures
your compiler(s)?". When you use SUPER-MAINT it will call the bogus
programs to create bogus files. Use the bogus debugger to see whether
"debugging information" was included (as a test of the -d and -n flags).
IMPORTANT NOTE: Do NOT try to run bogus .EXE files, and do NOT link
bogus .OBJ or .LIB files into real programs!
Bogus C Compiler: EBCL.EXE
Bogus Assembler: EBMASM.EXE
Bogus Linker: EBLINK.EXE
Bogus Librarian: EBLIB.EXE
Bogus Debugger: EBDB.EXE
--------
****************************[ 5. THE FUTURE ]******************************
If there are features you would like in SUPER-MAINT please don't hesitate
to say so. Please don't be angry at the program for not doing something
you want it to do. Instead let us know what you want and there is a very
good chance it will be included in future versions. We try to include as
many users' suggestions into my programs as is reasonable (given the scope
of the program). So please keep those cards and letters coming!
*************************[ 6. THE SAMPLE PROGRAM ]*************************
Included with this package is a set of sample files that you can use to
experiment with. These consist of:
SAMPLE.C C Code
SAMPLE1.C C Code
SAMPLE2.C C Code
SAMPLE.EXE An executable version.
SAMPLE.EXE is a simple multi moduled program addition using C language.
It contains 5 functions.
To call it you type SAMPLE and two numbers (ex: SAMPLE 5 67). It will
add the numbers and report on whether it is exiting properly or with
an error condition.
*********************[ Programmer's SUPER-MAINT ]***************************
***************************[ version 3.00 ]*********************************
************************[ End of README File ]******************************